The document tree area of the Document System lists the folders available in the current view of the Document System. The folders that are visible depend on the roles and groups assigned to your user record as well as by what feature of iMIS you are using. The full extent of the folders available in the Document System can be seen only by SysAdmins.
Multiple hierarchies, different roots
There are several Document System hierarchies, each used for different areas of iMIS:
■ $/ — Business Object Designer (BOD) has its own hierarchy of business objects. The root is represented by a $ character.
■ @/ — Content folders and content records exist in their own hierarchy. The root is represented by a @ character.
■ ~/ — Sitemaps each exist as their own hierarchy. The roots are represented by ~ characters.
■ $/— All other definition objects exist in the main Document System hierarchy, portions of which are also exposed in other features of iMIS. The root is represented by a $ character.
Tasks that you can perform
■ Click an item to select it for use with a toolbar command and to display a read-only summary of its basic properties in the summary area.
■ Double-click a folder to open the folder and display its contents.
Toolbar behavior when folders are selected
When a folder in the document tree area is selected, the toolbar commands behave as follows:
■ Organize > Refresh refreshes the document tree.
■ Organize > Cut, Organize > Copy, and Organize > Paste enable you to copy or move entire folders, including all of their descendants. The cut or copied folder and all of its descendants are placed inside the folder that is selected when you use the Organize > Paste command.
■ Organize > Select All selects all contents within the selected folder.
■ Organize > Delete moves the selected folder and all of its descendants to the Recycle Bin.
■ Organize > Properties shows a read-only summary of the selected folder's basic properties.
■ Organize > Display Summary shows or hides the summary panel for the object selected.
■ New displays a drop-down list from which you can choose a new folder or definition object type to create in the selected folder. When you select an object type, a properties window appears in which you can define the object. The object types shown in the drop-down list are determined by the properties of the selected folder, which you can examine by using the Edit toolbar command.
■ Edit opens a window that enables you to edit the definition of the selected folder.
■ Import imports an external XML file (created by the Export command on a different iMIS database) into objects in the Document System. (You cannot use Export and Import to make copies of objects within the same iMIS database.)
The Upload button reads the XML file contents and displays a list of the definition objects that were exported to the XML file. You can select which of the objects to import, and whether to overwrite objects with the same database GUID in the destination folder or to create new copies of the objects. You can also opt to import the objects to the folder from which they were originally exported, or to override that default destination with the selected folder.
For versioned document types, if a newer version of the object exists in the Document System, then the newer version is not overwritten during the import. Instead, the imported object is added as an archived version of the object. To replace the newer version of the object with the imported object, select Versions from the toolbar, choose the correct version, and click Revert.
■ Export exports all selected folders and definition objects into a single XML file, which can later be used to import those objects into the same folder or a different folder in a different iMIS database. (You cannot use Export and Import to make copies of objects within the same iMIS database. To make copies, use Organize > Copy and Organize > Paste.)
■ Versions displays a list of the existing versions of the folder, from which you can:
□ Export a specific version to an XML file.
□ Purge a specific version from the version list, removing all traces of that version from the system.
□ Copy a specific version to a new folder with a different name.
□ Create an new version based on any existing version by selecting the version, clicking Revert (which creates a new working version), and then publish the working version. If you make no changes to the working version you are effectively reverting to the state of the selected version, although technically it becomes a more recent version in the list of versions.
■ Run cannot be used in this context. You must use this command from the folder contents area.
■ Publish transforms all working versions of the descendant definition objects in the selected folder into published versions of those objects. Only the most recent published version (of a versionable object) is actively used by the system. You must select the Publish children as well? checkbox when publishing a folder.
To manage folders and objects in the Recycle Bin
Folders and definition objects that have been deleted are moved to the Recycle Bin at the bottom of the Document System hierarchy.
■ To permanently delete individual folders and definition objects that you do not think you'll ever need again, select an object listed in the recycle bin and from the toolbar choose Organize > Purge. To permanently delete the entire contents of the recycle bin, select the Recycle Bin itself and from the toolbar choose Organize > Empty the Recycle Bin.
■ To restore a deleted definition object, select it and from the toolbar choose Versions. In the version history that appears, click the Recycled version at the top of the list and click Revert. The definition object is moved to its original parent folder in the hierarchy, and its status changes to Working. You must then re-publish the definition object to make it active again.
Note: If the definition object's original parent folder no longer exists, the restored object is placed in the root folder of the Document System hierarchy. You must move it out of the root into another folder before you'll be able to publish the object.